This repository has been archived by the owner on Apr 25, 2023. It is now read-only.
Emit query log in quaint:query span, rather than in its parent #431
+9
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracked in https://github.com/prisma/client-planning/issues/158
Addressed the problem expressed in https://github.com/prisma/client-planning/issues/158#issuecomment-1405530608
Before this change query log events where not attached to the
quaint:query
span but its parent. This had implications on log capturing. mainly, thatBEGIN
iTX queries where not logged until its owner span (itx_runner) was not closed at the end of the transaction.